Git and github for poets (the coding train series)

Youtube series
Git is a version controller (of files), it has a lot of features for making
collaboration really nice.

1.1 Introduction

GIt

Is the actual version controller software, invented by the guy who invented
Linux.

Github

Web site/social network where you can do projects that have version control on them

This key concepts are shown in the video using only github

Key concepts

• Repository: repository of stuff
• Commit: think of this as a save
• Commit hash: unique identifier for a particular commit

1.2 Branches

Branch

Think of the history of a project as a tree. Branches are separate paths

Key concepts

• Master: main line of the thistory
• Commit depending on the branch: commitements are branch independent
• Graph > network shows the tree history of the project
• Pull request: take some changes from a particular branch and bring them
  into another branch
• Merge

1.3 Forks and Pull requests

• Fork: taking an entire other instance of a repo and get an exact replica
  on another account
• Pull request: request to pull changes to main account

1.4 Github issues

Not a git concept, it's just a feature available in github. Supports markdown. They
do have identifiers, a commit may refer to it. Can be used to identify bugs, or
comments about a project in general.

1.5 Intro to command line

No further new information :)

1.6 Cloning repo and push/pull

You can use Git in your own local computer.

Key concepts

• Clone: the act of taking a repository that is on a server like Github and cloning it
  into your own computer.
• Push: is the act of sending to Github
• Pull: the act of receiving grom Github
• Remote: A duplicate instance of your respository that lives somewhere else in a remote server

Commands

• git: before the use of any command
• git + clone +httpp//something//blahblah clones a repository into the folder where you execute the command
• git+status can only be executed when you're located inside a repository, and returns thte status of the repository.
• git +commit local commitment
• Easy way to getting started save all changes git commit -a
• -m "Changes" usual flag to add a message in the previous commnad
• git config --global user.name "Your Name" set the name of the author
• git config --global user.email "you@example.com" set the email of the author
• git config --list list all the cofiguration settings on the local computer
• git+ log list all the commitments (like viewing tree)
• : q in case you get stuck within VIM
• git+remote lists all the remotes associated with my project
• git+remote+-v verbose
• The way of pushing locally is:
  git+push+origin+branch branch could be master, etc.

1.7 Git init and git add

Key concepts
Save and commit are different steps. Save is the act of modifying the file on the hard drive, commiting is the act of adding that change to the story of the repository.

• Stage area: is the place where changes are kept before deciding whether a change will be commited or not.

Commands

• git+init: turn a directory into a repository
  After having executed previous command you must add the files that you want to be tracked
• git+add+"file.ext" : adds file to the staging area
• git+add+. add everything inside the repo to the staging area, so files can be tracked.

If we want to upload this changes to a Github repository we can't use git push origin master because we didn't clone the repo from an existing one in Github.
What we have to do, then?

First create a host repository in Github, after that execute the following commands:

• git remote add origin+url
• git push origin master
  And that's it.
• git pull origin main pulls all the changes made in the remote copy of the repository